Check if this issue is valid — if so, understand the root cause and fix it. At apps/app/src/components/integrations/CloudShellSetup.tsx, line 89:

<comment>When `disabled` is true, the "Show full script..." button still renders but does nothing — clicking it sets `expanded` without any visible effect since the `<pre>` always shows `disabledMessage`. Hide the expand/collapse button when disabled.</comment>

<file context>
@@ -74,7 +86,7 @@ export function CloudShellSetup({
         <div className="px-3 py-2.5">
           <pre className="text-[11px] font-mono leading-relaxed text-foreground/70 whitespace-pre-wrap break-all">
-            {expanded ? finalScript : previewLines}
+            {disabled ? disabledMessage : expanded ? finalScript : previewLines}
           </pre>
           {!expanded && (
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/app/src/app/(app)/[orgId]/integrations/[slug]/components/EmptyStateOnboarding.tsx, line 622:

<comment>Hardcoded step numbers produce a gap (2, 3, 4) when `awsTypeFields` is empty. For non-AWS cloud providers that don't have an `awsType` field, Step 1 is hidden but subsequent steps still display as 2, 3, 4. Consider computing step numbers dynamically based on which sections are visible.</comment>

<file context>
@@ -542,25 +596,48 @@ function CloudSetup({
             <div className="p-6 space-y-4">
-              <StepHeader step={1} title="Create IAM Role" />
-              <CloudShellSetup script={provider.setupScript} externalId={orgId} />
+              <StepHeader step={2} title="Create IAM Role" />
+              <CloudShellSetup
+                script={setupScript}
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/api/src/openapi/public-docs-quality.ts, line 81:

<comment>Filter Path Item entries to HTTP methods only before running operation quality checks; otherwise non-operation fields are incorrectly reported as missing summaries/metadata.</comment>

<file context>
@@ -0,0 +1,120 @@
+  const exposedTags = new Set<string>();
+
+  for (const [routePath, methods] of Object.entries(document.paths)) {
+    for (const [method, op] of Object.entries(
+      methods as Record<string, OperationForQuality>,
+    )) {
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/api/src/main.ts, line 177:

<comment>Applying public-docs metadata to the runtime Swagger document forces the server URL to production, overriding the environment-specific `baseUrl` and making non-prod `/api/docs` point at prod.</comment>

<file context>
@@ -169,6 +174,8 @@ async function bootstrap(): Promise<void> {
     .build();
   const document: OpenAPIObject = SwaggerModule.createDocument(app, config);
 
+  applyPublicOpenApiMetadata(document);
+
   // Setup Swagger UI at /api/docs
</file context>